• PS3 Controller Will Not Pair v4.7.7

    Help and Support
    15
    1 Votes
    15 Posts
    1k Views
    P

    @mitu yes, I removed all device from the menu “Remove Bluetooth Device”.
    I’m going crazy trying to solve!

  • 0 Votes
    2 Posts
    435 Views
    S

    ok I'm an idiot....I didn't realize when I first mapped my ps3 control to retropie - that the ps3 controller numbers are right there as well..dpad up is 13, dpad 14, then I just needed to go to the dapinput.ini and add 1 to all the numbers since 0 is an unmapped number

  • 0 Votes
    11 Posts
    2k Views
    F

    @yfzdude

    Awesome, thanks a bunch dude. This is a good setup, appreciate the help.

  • 0 Votes
    8 Posts
    849 Views
    pjftP

    @tzinck the link I shared mentioned how to retrieve the verbose log.

  • 0 Votes
    3 Posts
    419 Views
    mituM

    Please don't post the same topic multiple times.

  • 0 Votes
    1 Posts
    450 Views
    No one has replied
  • Sometimes does not work?

    Help and Support
    18
    0 Votes
    18 Posts
    3k Views
    D

    @clyde "focus on hover" using this choice...

  • 0 Votes
    2 Posts
    465 Views
    T

    I've tried using the xboxdrv and these are my results (any help at this point is helpful):

    cat /proc/bus/input/devices

    List of Devices:

    First Device:
    N: Name="Sony PLAYSTATION(R)3 Controller Motion Sensors"
    H: Handlers=event1

    Second Device:
    N: Name="Sony PLAYSTATION(R)3 Controller"
    H: Handlers=event2 js0

    ls /dev/input/by-id/

    event location by name for later use

    List of Devices:

    Fist Device:
    usb-Sony_PLAYSTATION_R_3_Controller-event-if00

    Second Device:
    usb-Sony_PLAYSTATION_R_3_Controller-event-joystick

    evtest /dev/input/event[•]

    I ended up trying evtest /dev/input/event1 for N: Name="Sony PLAYSTATION(R)3 Controller Motion Sensors". This did not work.

    evtest /dev/input/event2

    This command works.

    The device I'll be working with from now on is the following:

    Second Device:
    N: Name="Sony PLAYSTATION(R)3 Controller"
    H: Handlers=event2 js0

    List of control input buttons and ABS codes begin here.

    D-Pad:

    BTN_DPAD_UP
    BTN_DPAD_DOWN
    BTN_DPAD_LEFT
    BTN_DPAD_RIGHT

    Buttons:

    BTN_SOUTH
    BTN_EAST
    BTN_WEST
    BTN_NORTH

    BTN_START
    BTN_SELECT

    Bumpers:

    BTN_TL
    BTN_TR

    Triggers:

    BTN_TL2
    ABS_Z
    BTN_TR2
    ABS_RZ

    Analog Sticks:

    BTN_THUMBL
    BTN_THUMBR

    ABS_X
    ABS_Y
    ABS_RX
    ABS_RY

    In the end, I ended up placing this in the /etc/rc.local file

    #!/bin/sh -e # # rc.local # # This script is executed at the end of each multiuser runlevel. # Make sure that the script will "exit 0" on success or any other # value on error. # # In order to enable or disable this script just change the execution # bits. # # By default this script does nothing. sudo /opt/retropie/supplementary/xboxdrv/bin/xboxdrv \ --evdev /dev/input/by-id/usb-Sony_PLAYSTATION_R_3_Controller-event-joystick \ --silent \ --detach-kernel-driver \ --force-feedback \ --deadzone-trigger 15% \ --deadzone 4000 \ --trigger-as-button \ --mimic-xpad \ --dpad-as-button --evdev-absmap ABS_X=x1,ABS_Y=y1,ABS_RX=x2,ABS_RY=y2,ABS_Z=lt,ABS_RZ=rt \ --evdev-keymap BTN_SOUTH=a,BTN_EAST=b,BTN_WEST=x,BTN_NORTH=y,BTN_TL=lb,BTN_TR=rb,BTN_THUMBL=tl,BTN_THUMBR=tr,BTN_SELECT=back,BTN_START=start,BTN_DPAD_UP=du,BTN_DPAD_DOWN=dd,BTN_DPAD_LEFT=dl,BTN_DPAD_RIGHT=dr \ --ui-buttonmap guide=void \ & exit 0

    And even then, I can't get retropie to recognize my controller as anything other than a playstation 3 controller AND now retropie won't finish rebooting.

    It gets stuck after a message stating:

    "You Xbox/Xbox360 controller should now be available as:
    /dev/input/js1
    /dev/input/event3

    Press Ctrl-C to quit"

    And then the next 3 lines are about Samba NMB Daemon being Started, Starting, and Started again. At this point the boot ceases all function.

    When I try the following command I get the same error message at boot.

    #!/bin/sh -e # # rc.local # # This script is executed at the end of each multiuser runlevel. # Make sure that the script will "exit 0" on success or any other # value on error. # # In order to enable or disable this script just change the execution # bits. # # By default this script does nothing. sudo /opt/retropie/supplementary/xboxdrv/bin/xboxdrv \ --evdev /dev/input/event2 \ --silent \ --detach-kernel-driver \ --force-feedback \ --deadzone-trigger 15% \ --deadzone 4000 \ --trigger-as-button \ --mimic-xpad \ --dpad-as-button --evdev-absmap ABS_X=x1,ABS_Y=y1,ABS_RX=x2,ABS_RY=y2,ABS_Z=lt,ABS_RZ=rt \ --evdev-keymap BTN_SOUTH=a,BTN_EAST=b,BTN_WEST=x,BTN_NORTH=y,BTN_TL=lb,BTN_TR=rb,BTN_THUMBL=tl,BTN_THUMBR=tr,BTN_SELECT=back,BTN_START=start,BTN_DPAD_UP=du,BTN_DPAD_DOWN=dd,BTN_DPAD_LEFT=dl,BTN_DPAD_RIGHT=dr \ --ui-buttonmap guide=void \ & exit 0

    I hope this information helps clarify my issue with this controller.

  • 0 Votes
    20 Posts
    5k Views
    K

    Reading the replies from @doug and @b3n, I've managed to implement the fix by giving a change to the report when the controller is connected.

    [48361.273580] usb 1-2.4: USB disconnect, device number 25 [48366.681972] usb 1-2.4: new full-speed USB device number 26 using xhci_hcd [48366.883070] usb 1-2.4: New USB device found, idVendor=054c, idProduct=0268, bcdDevice= 0.01 [48366.883092] usb 1-2.4: New USB device strings: Mfr=0, Product=2, SerialNumber=0 [48366.883102] usb 1-2.4: Product: PS3 Controller [48366.890323] usbhid 1-2.4:1.0: can't add hid device: -32 [48366.890366] usbhid: probe of 1-2.4:1.0 failed with error -32 [48366.905149] usb 1-2.4: USB disconnect, device number 26 [48367.449946] usb 1-2.4: new full-speed USB device number 27 using xhci_hcd [48367.643118] usb 1-2.4: New USB device found, idVendor=054c, idProduct=0268, bcdDevice= 5.72 [48367.643141] usb 1-2.4: New USB device strings: Mfr=0, Product=2, SerialNumber=0 [48367.643150] usb 1-2.4: Product: PS3 Controller [48367.654388] input: PS3 Controller Motion Sensors as /devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2.4/1-2.4:1.0/0003:054C:0268.0014/input/input47 [48367.706730] input: PS3 Controller as /devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2.4/1-2.4:1.0/0003:054C:0268.0014/input/input46 [48367.707515] sony 0003:054C:0268.0014: input,hiddev98,hidraw6: USB HID v81.11 Joystick [PS3 Controller] on usb-0000:00:14.0-2.4/input0

    Good: The driver works even with the latest driver available. It just change the report of the given controller, so, other controllers will remain functional.

    Bad: The controller only works with the cable and the player's count LEDs turn on in a weird way.

    TODO: I still want to make this driver actually doable. Any help will be very welcome.

    GitHub: https://github.com/KanuX-14/GeneriKit

    Edit: The original driver will be kept. It can be enabled again by deleting the line 'blacklist hid-sony' in /etc/modprobe.d/generikit.conf.

  • 0 Votes
    4 Posts
    4k Views
    mituM

    @soda-inc said in How do I enable force feedback / rumble?:

    Also, I found some old posts which indicated that the Retropie Kernel might not be setup for controller vibration support.

    There's no RetroPie kernel and there's no special configuration that disables controller vibration support (as you've noticed with N64).

    When starting a PS1 game, check if you have 'Enable Vibrarion' in the Core settings and also set the Pad 1 Type to Dualshock.

  • 0 Votes
    11 Posts
    1k Views
    F

    @mitu Yes i have the default file present.

  • 0 Votes
    2 Posts
    322 Views
    mituM

    Can you add more details about your system, as detailed in https://retropie.org.uk/forum/topic/3/read-this-first ?

  • 0 Votes
    8 Posts
    906 Views
    K

    @mitu OK thanks

  • Dual PS3 usb controller problem

    Help and Support
    1
    0 Votes
    1 Posts
    57 Views
    No one has replied
  • 0 Votes
    8 Posts
    941 Views
    D

    @psyke83
    Updated to version 4.6.1, and sixaxis is working like a charm!!!
    Thank you. =)

  • 0 Votes
    6 Posts
    530 Views
    mituM

    Have you updated RetroPie and/or the OS packages ? Try running and update and say 'Yes' when asked to upgrade the OS/packages. You don't need pulseaudio for pairing a mouse/keyboard, you should remove that.

  • 0 Votes
    1 Posts
    252 Views
    No one has replied
  • 0 Votes
    11 Posts
    781 Views
    J

    @psyke83

    Love this community. Thanks for a fast response @psyke83 & @mitu.

    I ended up hacking your hack in sixaxis-helper.sh.
    I basically disabled the whole restart and renaming section by commenting it out.

    sixaxis_rename() { local bt_profile="/var/lib/bluetooth/${BLUETOOTH_MAC^^}/${SIXAXIS_MAC^^}/info" if [[ "$(grep -e "^Name=PLAYSTATION(R)3 Controller" -e "^Trusted=true" -c "$bt_profile" 2>/dev/null)" == "2" ]]; then echo "BlueZ <5.48 hack: renaming BT profile to make consistent with kernel module name" # systemctl stop bluetooth # sed 's/.*Name=PLAYSTATION(R)3 Controller.*/Name=Sony PLAYSTATION(R)3 Controller/' -i "$bt_profile" # systemctl start bluetooth exit 0 fi }

    The controller paired then.
    but like you stated I had to re-config the controller inputs (for BT vs USB).

    Digging deeper I compared the two files under var/lib/bluetooth/${BLUETOOTH_MAC^^}/${SIXAXIS_MAC^^}/info for the On-board BT and the Dongle BT addresses.

    The file for the on-board BT holds the changes to the renaming "Sony PLAYSTATION(R)3 Controller"
    But for the BT dongle - on restart it must overwrite the file again with the old name "PLAYSTATION(R)3 Controller".

    Anyway I have a fix that works for me.

  • 0 Votes
    1 Posts
    673 Views
    No one has replied
  • 0 Votes
    7 Posts
    1k Views
    chubstaC

    @tpo1990 said in connect PS3 controller via usb - cable help!:

    For me. I like to use the original hardware with my RetroPie setup so i get the most authentic experience.

    Yeah, I am the same, it is all part of the nostalgia